Systems and methods for providing near field communications

ABSTRACT

Methods and systems are disclosed for providing Near Field Communications. In certain embodiments, an Android mobile operating system based mobile device is configured with software that, when executed by one or more processors, determines whether the mobile device is to perform an NFC communication with a contactless payment terminal (CPT) using a secure element associated with an NFC controller included in the mobile device. Based on the determination, the mobile device is configured to execute software that performs communications with the CPT using the NFC controller.

PRIORITY CLAIM

This disclosure claims priority under 35 U.S.C. §119 to U.S. provisionalpatent application No. 61/702,230, filed on Sep. 17, 2012, and entitled“System and Methods for Providing Near Field Communications,” which isincorporated herein by reference in its entirety.

TECHNICAL FIELD

The disclosed embodiments generally relate to communication systems and,more particularly, to processes and systems for providing near fieldcommunications with or without the use of a secure element.

BACKGROUND

Currently, mobile device operating systems are configured to detect onlya handful of ISO-14443 device types to facilitate near-fieldcommunications (NFCs). NFC is a short-range radio technology thatenables wireless communication between devices. NFC is an open-platformtechnology and is based on and extends on RFID technologies. But somedevices using the ISO-14443 standard, including Proximity CouplingDevices (PLDs), remain unsupported by certain operating systems, such asAndroid™. Thus, to detect and use these unsupported devices, use of asecure element, which provides an environment in which data/processesmay be securely stored and/or executed, must be sacrificed.

Accordingly, there is a need for systems and processes that enabledevices, such as mobile devices using an Android™ operating system, tocommunicate with PCDs using a secure element.

SUMMARY

Methods and systems consistent with the disclosed embodiments provideNFC capabilities through software that, when executed by a processor,allow a mobile device to request that a PCD be detected, and ultimatelycommunicated with, using a secure element despite employing an operatingsystem that does not support PCDs. According to some embodiments, themobile device may initialize a discovery mode to detect and ultimatelycommunicate with a PCD to perform a transaction, such as a financialtransaction, with or without the secure element.

Additional objects and advantages will be set forth in part in thedescription which follows, and in part will be obvious from thedescription, or may be learned by practicing embodiments of the presentdisclosure. The objects and advantages will be realized and attained bymeans of the elements and combinations particularly pointed out in theappended claims.

Consistent with disclosed embodiments, a mobile device for processingtransactions is disclosed. The mobile device may comprises a processorand memory storing instructions that, when executed by the processor,perform operations. The operations performed by the mobile device mayinclude initializing a discovery mode to detect the contactless paymentterminal and, once detected, identifying a near field communicationprotocol associated with the contactless payment terminal. Theoperations performed by the mobile device may also include providing aselection to the user regarding whether or not to use a secure elementto perform the transaction when the near field communication protocol isnot supported by an operating system associated with the mobile device.Finally, the operations performed by the mobile device may includeconducting the transaction based at least on the user selection.

Consistent with disclosed embodiments, a method is disclosed forprocessing transactions. The method may comprise initializing adiscovery mode to detect the contactless payment terminal andidentifying a near field communication protocol associated with thecontactless payment terminal. The method may also include providing aselection to the user regarding whether or not to use a secure elementto perform the transaction when the near field communication protocol isnot supported by an operating system associated with the mobile device.Finally, the method may include conducting the transaction based atleast on the user selection.

Consistent with disclosed embodiments, a non-transitorycomputer-readable medium is disclosed storing instructions that, whenexecuted by a processor, cause the processor to perform operations. Theoperations may include initializing, via one or more processors, adiscovery mode to detect the contactless payment terminal. Further, theoperations may include identifying a near field communication protocolassociated with the contactless payment terminal and providing aselection to the user regarding whether or not to use a secure elementto perform the transaction when the near field communication protocol isnot supported by an operating system associated with the mobile device.Finally, the operations may include conducting, via the one or moreprocessors, the transaction based at least on the user selection.

Consistent with other disclosed embodiments, tangible computer-readablestorage media may store program instructions that are executable by oneor more processors to implement any of the processes disclosed herein.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory only,and are not restrictive of the disclosed embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate several embodiments and, togetherwith the description, serve to explain the disclosed principles. In thedrawings:

FIG. 1 is a diagram of an exemplary system that may be used to implementthe disclosed embodiments.

FIG. 2 is a flowchart of an exemplary process flow consistent with thedisclosed embodiments.

FIG. 3 is a flowchart of an exemplary process flow consistent with thedisclosed embodiments.

FIG. 4 is a flowchart of an exemplary process flow consistent with thedisclosed embodiments.

DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to exemplary embodiments, examplesof which are illustrated in the accompanying drawings and disclosedherein. Wherever convenient, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts.

FIG. 1 shows an exemplary system 100 that is configured to perform oneof more software processes that, when executed by a processor, provideone or more aspects of the disclosed embodiments. The components andarrangements shown in FIG. 1 are not intended to be limiting to thedisclosed embodiment, as the components used to implement the disclosedprocesses and features disclosed here may vary.

In one embodiment, system 10000 includes a mobile device 100 andcontactless payment terminal (CPT) 300. The components of mobile device100 may be implemented in hardware, software, or a combination of bothhardware and software, as will be apparent to those skilled in the art.In accordance with certain disclosed embodiments, mobile device 100 maybe a mobile computer-based system, such as, for example, cellulartelephone, tablets, hand held computing devices (e.g., smart phones),tablets, laptops, and any other type of mobile computer-based system.Alternatively, mobile device 100 may be configured as a particularapparatus, embedded system, dedicated circuit, and the like based on thestorage, execution, and/or implementation of the software instructionsthat perform one or more operations consistent with the disclosedembodiments. According to some embodiments, mobile device 100 mayinclude one or more processors 101, memory 107 storing an operatingsystem 102 and one or more software programs 103, an input/outputcomponent 104, and a near field communication (hereinafter “NFC”)controller 105 with a secure element 106. For example, mobile device 100may be a contactless integrated circuit cards using the ISO-14443standard. In other embodiments, mobile device 100 may be an NFC-enabledsmart phone emulating a contactless financial card or keyfob. Othercomponents known to one of ordinary skill in the art may be included inmobile device 100 to process, transmit, provide, and receive informationconsistent with the disclosed embodiments.

Processor(s) 101 may be one or more known processing devices, such as amicroprocessor from the Pentium™ family manufactured by Intel™ or theTurion™ family manufactured by AMD™. Processor(s) 101 may include asingle core or multiple core processor system that provides the abilityto perform parallel processes simultaneously. For example, processor 101may be a single core processor that is configured with virtualprocessing technologies known to those skilled in the art. In certainembodiments, processor 101 may use logical processors to simultaneouslyexecute and control multiple processes. Processor 101 may implementvirtual machine technologies, or other similar known technologies toprovide the ability to execute, control, run, manipulate, store, etc.multiple software processes, applications, programs, etc. In anotherembodiment, processor(s) 101 may include a multiple-core processorarrangement (e.g., dual or quad core) that is configured to provideparallel processing functionalities to allow mobile device 100 toexecute multiple processes simultaneously. One of ordinary skill in theart would understand that other types of processor arrangements could beimplemented that provide for the capabilities disclosed herein.

Mobile device 100 may include one or more storage devices configured tostore information used by processor 101 (or other components) to performcertain functions related to the disclosed embodiments. As discussedabove, for example, memory 107 may store instructions to enableprocessor(s) 101 to execute software, such as one or more applications,network communication processes, operating system software, and anyother type of application or software known to be available on mobiledevices. Memory 107 may be a volatile or non-volatile, magnetic,semiconductor, tape, optical, removable, nonremovable, or other type ofstorage device or tangible computer-readable medium. In one embodiment,operating system 102 is an Android™ operating system for mobile devices.

NFC controller 105 may be a device with logic that is configured toexecute NFC-related operations. Alternatively, NFC controller 105 may besoftware that is stored in memory 107, or a separate memory device inmobile device 100. NFC controller 105 may operate and be configuredaccording to architectures and designs known to one of ordinary skill inthe art. In one embodiment, NFC controller 105 includes a secure element106 providing an environment in which processes and data may be securelystored and/or executed. In other embodiments, secure element 106 may beseparate from NFC controller 105, such as a separate embedded device inthe mobile device, a SIM/UICC card that functions as the secure element,or software located in memory that may or may not be the same memorythat hosts NFC controller 105. For example, secure element 106 mayprovide delimited memory for applications operating according todisclosed embodiments. In certain embodiments, secure element 106 isconfigured and operates as known secure elements for NFC devices. Forexample secure element 106 may store applications, credentials (e.g.,usernames and/or passwords), and/or other information associated withsecure execution of applications.

I/O 104 may be one or more components that enable mobile device 100 tocommunicate with external devices. I/O 104 may include input/outputcomponents known to those skilled in the art. For example, I/O devices104 may be one or more devices configured to allow data to be receivedand/or transmitted by mobile device 100. I/O devices 304 may include oneor more digital and/or analog devices that allow mobile device 100 tocommunicate with other machines and devices, such as other components ofsystems 1000. For example, I/O devices 104 may include a screen fordisplaying NFC communication payment methods or providing information tothe user. I/O devices 104 may also include one or more digital and/oranalog devices that allow a user to interact with mobile device 100,such as a touch-sensitive area, buttons, or microphones. I/O devices 104may also include one or more accelerometers to detect the orientationand inertia of mobile device 100. I/O devices 104 may also include othercomponents known in the art for interacting with other components ofsystem 1000.

Contactless payment terminal (CPT) 300 may be any known NFC devicedesigned to communicate with mobile device 100. For example, CPT 300 maybe a “contactless payment terminal,” such as point of sale terminal,automated teller machine, signage, RFID or similar tag mounted on anytype of equipment, product, person, and the like, or any other devicethat is configured to communicate with NFC mobile devices to facilitatea financial transaction that are known in the art. As shown, in someembodiments, CPT 300 may include a display 301. Display 301 may showinformation regarding transactions, such as amounts due for a purchaseand may further display information confirming receipt of payment.

FIG. 2 shows a flowchart of an exemplary process that may be performedby mobile device 100 consistent with certain embodiments. In one aspect,processor(s) 101 may execute software stored in memory 107 (or anothermemory) to perform NFC communications consistent with the disclosedembodiments. For exemplary purposes, disclosed embodiments are discussedin the context of financial transactions. Disclosed embodiments,however, are not limited to financial transactions and may include, forexample, product tracking, information collecting (e.g., retrieving datafrom a sign, document, etc, configured with CPT capabilities), etc.

At step 210, mobile device 100 may be configured to execute softwarethat receives a user command to initiate a financial transaction. Forexample, the mobile device may have received a user command to initiatea program associated with NFC and/or financial transactions. In otherembodiments, mobile device 100 may become prompted by a message from CPT300 regarding a potential upcoming financial transaction. At step 220,mobile device 100 may generate a query that is presented on a displaydevice of mobile device 100. In one aspect, the query may request aresponse indicating whether mobile device 100 is to communicate with aCPT (e.g., CPT 300) using the NFC secure element 106. Mobile device 100may then receive an indication in response to the query whether furthercommunication with the CPT 300. If the response indicates thatcommunication should be made (step 220; NO), the process may end.Otherwise (step 220; YES), mobile device 100 may execute software toinitiate a discovery mode to identify one or more CPTs 300 with which tocommunicate (step 230). Upon detection of at a CPT 300 (step 240),mobile device 100 may execute software to identify the NFC protocolemployed by the CPT 300 (step 250).

If the identified NFC protocol is supported by the operating system ofmobile device 100 (step 260; YES), the process may continue as shown inFIG. 4. As shown in FIG. 4, the mobile device 100 may use the operatingsystem to follow the appropriate NFC communication and/or ISO standards(step 410) to perform one or more transactions with the detected CPT 300(step 420). According to some embodiments, any type of transaction maybe performed, such as financial, product tracking, informationcollecting (e.g., retrieving data from a sign, document, etc, configuredwith CPT capabilities), etc.

If the identified NFC protocol is not supported by the operating systemof mobile device 100 (step 260; NO), the process may continue as shownin FIG. 3. According to some embodiments, mobile device 100 may employan Android™ operating system that lacks support for the detected PCT'sNFC protocol of ISO-14443 used for PCDs. As shown in FIG. 3, mobiledevice 100 may execute software that prompts the user as to whether thesecure element should be used to communicate with CPT 300 (step 310). Ifmobile device 100 receives an indication that the secure element shouldbe used (step 310; YES), mobile device 100 access an NFC controllerassociated with mobile device 100 (step 320). Mobile device 100 may alsoexecute software that conforms to the ISO standards associated with theidentified NFC protocol to access the secured element (step 330). Mobiledevice 100 may also execute software to confirm the mobile device iswithin a predetermined range of the CPT 300 (step 340) and, onceconfirmed, may communicate with the CPT 300 to conduct a transactionusing the secure element (step 350). In some aspects, the predeterminedrange is determined by the identified NFC protocol and/or associated ISOstandard. According to some embodiments, any type of transaction may beperformed, such as financial, product tracking, information collecting(e.g., retrieving data from a sign, document, etc. configured with CPTcapabilities), etc.

If mobile device 100 receives an indication that the secure elementshould not be used (step 310; NO), mobile device 100 may access an NFCcontroller associated with mobile device 100 (step 360). Mobile device100 may also execute software to confirm the mobile device is within apredetermined range of the CPT 300 (step 370) and, once confirmed, maycommunicate with the CPT 300 to conduct a transaction using the secureelement (step 380). In some aspects, the predetermined range isdetermined by the identified NFC protocol and/or associated ISOstandard. According to some embodiments, any type of transaction may beperformed, such as financial, product tracking, information collecting(e.g., retrieving data from a sign, document, etc. configured with CPTcapabilities), etc.

The disclosed embodiments, in certain aspects, may be implemented withmobile devices configured to execute the Android™ operating system formobile devices. Typical Android™ based NFC devices are not configured toperform communications with CPTs without going through a secure element.Aspects of the disclosed embodiments enable such Android™ based NFCdevices to selectively perform secure element communications inaccordance with known ISO standards or non-secure elementcommunications.

The foregoing description has been presented for purposes ofillustration. It is not exhaustive and is not limited to the preciseforms or embodiments disclosed. Modifications and adaptations of theembodiments will be apparent from consideration of the specification andpractice of the disclosed embodiments. For example, the describedimplementations include hardware and software, but systems and methodsconsistent with the present disclosure can be implemented as hardwarealone.

Computer programs based on the written description and methods of thisspecification are within the skill of a software developer. The variousprograms or program modules can be created using a variety ofprogramming techniques. For example, program sections or program modulescan be designed in or by means of Java, C, C++, assembly language, orany such programming languages. One or more of such software sections ormodules can be integrated into a computer system, computer-readablemedia, or existing communications software.

Moreover, while illustrative embodiments have been described herein, thescope includes any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations or alterations based on the presentdisclosure. The elements in the claims are to be interpreted broadlybased on the language employed in the claims and not limited to examplesdescribed in the present specification or during the prosecution of theapplication, which examples are to be construed as non-exclusive.Further, the steps of the disclosed methods can be modified in anymanner, including by reordering steps or inserting or deleting steps. Itis intended, therefore, that the specification and examples beconsidered as example only, with a true scope and spirit being indicatedby the following claims and their full scope of equivalents.

What is claimed is:
 1. A mobile device for processing transactions,comprising: a processor; and memory storing instructions that, whenexecuted by the processor, perform operations comprising: initializing adiscovery mode to detect a contactless payment terminal; identifying anear field communication protocol associated with the contactlesspayment terminal; providing a selection to the user regarding whether ornot to use a secure element to perform a transaction when the near fieldcommunication protocol is not supported by an operating systemassociated with the mobile device; and conducting the transaction basedat least on the user selection.
 2. The mobile device of claim 1, whereinthe memory stores instructions that, when executed by the processor,perform further operations comprising: conducting the transaction usingthe secure element when the user indicates a selection of the secureelement in response to the query.
 3. The mobile device of claim 1,wherein the memory stores instructions that, when executed by theprocessor, perform further operations comprising: requesting access to aNFC controller of the mobile device; and detecting, using the NFCcontroller, that the mobile device is within a predetermined range of aCPT.
 4. The mobile device of claim 1, wherein the memory storesinstructions that, when executed by the processor, perform furtheroperations comprising: conducting the transaction without using thesecure element when the user indicates a selection not to use the secureelement in response to the query.
 5. The mobile device of claim 1,wherein the transaction comprising at least one of a financial, producttracking, or information collecting transaction.
 6. The mobile device ofclaim 1, wherein the mobile device initializes the discovery mode basedon at least one of receiving a user command to initiate a programassociated with near field communication, receiving a user command toinitiate a program associated with financial transactions, or receivinga message from the contactless payment terminal regarding an upcomingfinancial transaction.
 7. A method for processing transactions,comprising: initializing, via one or more processors, a discovery modeto detect a contactless payment terminal; identifying a near fieldcommunication protocol associated with the contactless payment terminal;providing a selection to the user regarding whether or not to use asecure element to perform a transaction when the near fieldcommunication protocol is not supported by an operating systemassociated with the mobile device; and conducting, via the one or moreprocessors, the transaction based at least on the user selection.
 8. Themethod of claim 7, further comprising: conducting the transaction usingthe secure element when the user indicates a selection of the secureelement in response to the query.
 9. The method of claim 7, furthercomprising: requesting access to a NFC controller of the mobile device;and detecting, using the NFC controller, that the mobile device iswithin a predetermined range of a CPT.
 10. The method of claim 7,further comprising: conducting the transaction without using the secureelement when the user indicates a selection not to use the secureelement in response to the query.
 11. The method of claim 7, wherein thetransaction comprising at least one of a financial, product tracking, orinformation collecting transaction.
 12. The method of claim 7, whereininitializing the discovery mode is based on at least one of receiving auser command to initiate a program associated with near fieldcommunication, receiving a user command to initiate a program associatedwith financial transactions, or receiving a message from the contactlesspayment terminal regarding an upcoming financial transaction.
 13. Anon-transitory computer readable medium storing instructions that, whenexecuted by a processor, cause the processor to perform operationscomprising: initializing, via one or more processors, a discovery modeto detect a contactless payment terminal; identifying a near fieldcommunication protocol associated with the contactless payment terminal;providing a selection to the user regarding whether or not to use asecure element to perform a transaction when the near fieldcommunication protocol is not supported by an operating systemassociated with the mobile device; and conducting, via the one or moreprocessors, the transaction based at least on the user selection. 14.The medium of claim 13, further storing instructions for: conducting thetransaction using the secure element when the user indicates a selectionof the secure element in response to the query.
 15. The medium of claim13, further storing instructions for: requesting access to a NFCcontroller of the mobile device; and detecting, using the NFCcontroller, that the mobile device is within a predetermined range of aCPT.
 16. The medium of claim 13, further storing instructions for:conducting the transaction without using the secure element when theuser indicates a selection not to use the secure element in response tothe query.
 17. The medium of claim 13, wherein the transactioncomprising at least one of a financial, product tracking, or informationcollecting transaction.
 18. The medium of claim 13, wherein initializingthe discovery mode is based on at least one of receiving a user commandto initiate a program associated with near field communication,receiving a user command to initiate a program associated with financialtransactions, or receiving a message from the contactless paymentterminal regarding an upcoming financial transaction.